Get Human Task
AutomatR.OrchestratorActivities.GetHumanTask
The "Get Human Task" activity in AutomatR OrchestratorActivities retrieves information about a human task created for user input in a workflow. This is particularly useful when you need to access data or responses provided by users during a specific task.
Properties
| Name | Description |
|---|---|
| Input | |
| Task ID | Specifies the ID of the human task for which information is to be retrieved. String variables containing the task ID. |
| Queue Item GUID | Specifies the GUID of the queue item associated with the human task. String variables containing the queue item GUID. |
| Misc | |
| Display Name | Provides a customizable name for the activity displayed in the workflow. The display name enhances clarity and organization within the automation project. String variable or argument containing the desired display name. |
| Optional | |
| Delay | Specifies the amount of time (in seconds) to wait before executing the "Get Human Task" activity. This can be useful for handling synchronization issues. Integer variables containing the delay duration. Ex.: If the amount of time is 1000 milliseconds or 1 sec, i.e., 1. |
| Output | |
| FormData | Outputs the form data associated with the human task. Dictionary variables containing the form data fields and values. |
| FormJSON | Outputs the form data in JSON format. String variables containing the JSON representation of the form data. |
| Created On | Outputs the date and time when the human task was created. DateTime variables to store the creation timestamp. |
| Assigned To | Outputs the email ID of the user to whom the human task is assigned. String variables containing the assigned user's email ID. |
| Status | Outputs the result of the "Get Human Task" operation, indicating whether the task retrieval was successful or encountered errors. Variables of relevant types (e.g., Boolean variables) to store the operation result. |
How to use:
- Drag and drop the "Get Human Task" activity onto the workflow.
- Configure the properties by specifying the task ID and queue item GUID to retrieve information about the human task.
- Optionally, configure the delay for the desired waiting time before retrieving the human task information.
- Execute the workflow to obtain details such as form data, creation timestamp, and assigned user associated with the specified human task.
Example: Consider an example where the "Get Human Task" activity is used to retrieve information about a human task:
Get Human Task:
Task ID: "987654"
Queue Item GUID: "a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6"
FormData: humanTaskData
FormJSON: humanTaskJSON
Created On: taskCreationTimestamp
Assigned To: assignedUser
Status: isTaskRetrievedSuccessfully
In this example, the activity retrieves information about the human task with the specified task ID and queue item GUID. The form data, form JSON, creation timestamp, assigned user, and the result of the operation are stored in the respective variables for further handling in the workflow.
Note: Ensure that the "Get Human Task" activity is appropriately integrated into the workflow, and the provided task ID and queue item GUID are valid for the expected human task.